Enhanced payments for shipping

ABSTRACT

Systems, methods, apparatus, and computer program products are provided for initiating shipment of and payment for shipping a parcel. For example, in one embodiment, a customer/user can receive a message on a user device from a carrier that includes an authorization code for shipping a parcel. After the customer/user ships the parcel, the carrier can charge a variety of accounts for the shipping charges, including a wireless services provider associated with the user device. In another embodiment, the customer/user can interact with a kiosk to ship the parcel. In this embodiment, the carrier can also charge a variety of accounts for the shipping charges, including a wireless services provider.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 12/813,096, filed Jun. 10, 2010, which is hereby incorporated hereinin its entirety by reference.

BACKGROUND

With an ever-increasing desire for customer-friendly shipping options, aneed exits for a solution that allows customers to pay for shippingservices using a mobile device.

BRIEF SUMMARY

In general, embodiments of the present invention provide systems,methods, apparatus, and computer program products for the shipment ofparcels.

In accordance with one aspect, a method for shipping a parcel isprovided. In one embodiment, the method comprises (1) receiving a firstmessage transmitted from a user device requesting shipment of a parcel;(2) in response to receiving the first message, identifying an accountidentifier based at least in part on the first message, wherein theaccount identifier corresponds to an account associated with a user ofthe user device; (3) determining whether the account is valid; and (4)in response to a determination that the account is valid, generating andtransmitting a second message to the user device, wherein the secondmessage comprises an authorization code. In one embodiment, the methodmay also comprise (5) receiving shipping information that is generatedas the parcel is transported within a carrier's transportation andlogistics network, wherein the shipping information comprises a trackingidentifier and the authorization code; (6) in response to receiving theshipping information, determining whether the parcel is approved forshipment based at least in part on the authorization code; (7) inresponse to a determination that the parcel is approved for shipment,storing at least a portion of the shipment information in associationwith the tracking identifier, the authorization code, and the accountidentifier; (8) electronically determining shipping charges for shipmentof the parcel; and (9) electronically charging the shipping charges tothe account.

In accordance with another aspect, another method for shipping a parcelis provided. In one embodiment, the method comprises (1) receiving afirst message transmitted from a user device requesting shipment of aparcel; (2) in response to receiving the first message, identifying anaccount identifier based at least in part on the first message, whereinthe account identifier corresponds to an account associated with a userof the user device; and (3) determining whether the account is valid. Inone embodiment, the method also comprises (4) in response to adetermination that the account is valid, generating and transmitting asecond message to the user device, wherein the second message comprisesan authorization code; (5) receiving shipping information that isgenerated as the parcel is transported within a carrier's transportationand logistics network, wherein the shipping information comprises atracking identifier and the authorization code; and (6) electronicallycharging shipping charges to the account.

In accordance with yet another aspect, a computer program product forshipping a parcel is provided. The computer program product may compriseat least one computer-readable storage medium having computer-readableprogram code portions stored therein, the computer-readable program codeportions comprising executable portions configured to (1) receive afirst message transmitted from a user device requesting shipment of aparcel; (2) in response to receiving the first message, identify anaccount identifier based at least in part on the first message, whereinthe account identifier corresponds to an account associated with a userof the user device; (3) determine whether the account is valid; and (4)in response to a determination that the account is valid, generate andtransmit a second message to the user device, wherein the second messagecomprises an authorization code. The computer-readable program codeportions may also comprise executable portions configured to (5) receiveshipping information that is generated as the parcel is transportedwithin a carrier's transportation and logistics network, wherein theshipping information comprises a tracking identifier and theauthorization code; (6) in response to receiving the shippinginformation, determine whether the parcel is approved for shipment basedat least in part on the authorization code; (7) in response to adetermination that the parcel is approved for shipment, store at least aportion of the shipment information in association with the trackingidentifier, the authorization code, and the account identifier; (8)determine shipping charges for shipment of the parcel; and (9) chargethe shipping charges to the account.

In accordance with still another aspect, a computer program product forshipping a parcel is provided. The computer program product may compriseat least one computer-readable storage medium having computer-readableprogram code portions stored therein, the computer-readable program codeportions comprising executable portions configured to (1) receive afirst message transmitted from a user device requesting shipment of aparcel; (2) in response to receiving the first message, identify anaccount identifier based at least in part on the first message, whereinthe account identifier corresponds to an account associated with a userof the user device; and (3) determine whether the account is valid. Thecomputer-readable program code portions may also comprise executableportions configured to (4) in response to a determination that theaccount is valid, generate and transmit a second message to the userdevice, wherein the second message comprises an authorization code; (5)receive shipping information that is generated as the parcel istransported within a carrier's transportation and logistics network,wherein the shipping information comprises a tracking identifier and theauthorization code; and (6) charge shipping charges to the account.

In accordance with another aspect, a method for shipping a parcel isprovided. In one embodiment, the method comprises (1) receiving inputfrom a user requesting shipment of a parcel; (2) causing display of arequest for input identifying a method of payment for shipment of theparcel; (3) in response to causing display of the request for input ofthe method of payment for shipment of the parcel, receiving input (a)identifying an account for wireless services as the method of paymentand (b) a phone number associated with the account for wirelessservices; and (4) determining whether the account for wireless servicesis valid. In one embodiment, the method also comprises (5) in responseto a determination that the account for wireless services is valid,generating and transmitting a message to a mobile device associated withthe phone number, wherein the message comprises an authorization code;(6) causing display of a request for input of the authorization codetransmitted to the mobile device; and (7) receiving input from the useridentifying the authorization code.

In accordance with another aspect, another method for shipping a parcelis provided. In one embodiment, the method comprises (1) receiving inputfrom a user requesting shipment of a parcel; (2) causing display of arequest for input identifying a method of payment for shipment of theparcel; (3) in response causing display of the request for input of themethod of payment for shipment of the parcel, receiving inputidentifying an account for wireless services as the method of payment;(4) in response to receiving input identifying the account for wirelessservices as the method of payment, automatically initiatingcommunication with a mobile device associated with the account forwireless services; and (5) determining whether the account for wirelessservices is valid.

In accordance with still another aspect, a computer program product forshipping a parcel is provided. The computer program product may compriseat least one computer-readable storage medium having computer-readableprogram code portions stored therein, the computer-readable program codeportions comprising executable portions configured to (1) receive inputfrom a user requesting shipment of a parcel; (2) cause display of arequest for input identifying a method of payment for shipment of theparcel; (3) in response to causing display of the request for input ofthe method of payment for shipment of the parcel, receive inputidentifying (a) an account for wireless services as the method ofpayment and (b) a phone number associated with the account for wirelessservices; and (4) determine whether the account for wireless services isvalid. The computer-readable program code portions may also compriseexecutable portions configured to (5) in response to a determinationthat the account for wireless services is valid, generate and transmit amessage to a mobile device associated with the phone number, wherein themessage comprises an authorization code; (6) cause display of a requestfor input of the authorization code transmitted to the mobile device;and (7) receive input from the user identifying the authorization code.

In accordance with yet another aspect, another computer program productfor shipping a parcel is provided. The computer program product maycomprise at least one computer-readable storage medium havingcomputer-readable program code portions stored therein, thecomputer-readable program code portions comprising executable portionsconfigured to (1) receive input from a user requesting shipment of aparcel; (2) cause display of a request for input identifying a method ofpayment for shipment of the parcel; (3) in response causing display ofthe request for input of the method of payment for shipment of theparcel, receive input identifying an account for wireless services asthe method of payment; (4) in response to receiving input identifyingthe account for wireless services as the method of payment,automatically initiate communication with a mobile device associatedwith the account for wireless services; and (5) determine whether theaccount for wireless services is valid.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

Having thus described the invention in general terms, reference will nowbe made to the accompanying drawings, which are not necessarily drawn toscale, and wherein:

FIG. 1 is an overview of a system that can be used to practice variousembodiments of the present invention.

FIG. 2 is an exemplary schematic diagram of a carrier system accordingto one embodiment of the present invention.

FIG. 3 is an exemplary schematic diagram of a mobile device according toone embodiment of the present invention.

FIGS. 4-5 are flowcharts illustrating operations and processes that canbe used in accordance with various embodiments of the present invention.

FIG. 6 is an exemplary drop-box according to one embodiment of thepresent invention.

FIG. 7 shows exemplary input/output that can be produced via a mobiledevice according to one embodiment of the present invention.

DETAILED DESCRIPTION

Various embodiments of the present invention now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the inventions are shown. Indeed, theseinventions may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. Like numbers refer tolike elements throughout.

I. Methods, Apparatus, Systems, and Computer Program Products

As should be appreciated, various embodiments may be implemented invarious ways, including as methods, apparatus, systems, or computerprogram products. Accordingly, various embodiments may take the form ofan entirely hardware embodiment or an embodiment in which a processor isprogrammed to perform certain steps. Furthermore, variousimplementations may take the form of a computer program product on acomputer-readable storage medium having computer-readable programinstructions embodied in the storage medium. Any suitablecomputer-readable storage medium may be utilized including hard disks,CD-ROMs, optical storage devices, or magnetic storage devices.

Various embodiments are described below with reference to block diagramsand flowchart illustrations of methods, apparatus, systems, and computerprogram products. It should be understood that each block of the blockdiagrams and flowchart illustrations, respectively, may be implementedin part by computer program instructions, e.g., as logical steps oroperations executing on a processor in a computing system. Thesecomputer program instructions may be loaded onto a computer, such as aspecial purpose computer or other programmable data processing apparatusto produce a specifically-configured machine, such that the instructionswhich execute on the computer or other programmable data processingapparatus implement the functions specified in the flowchart block orblocks.

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including computer-readableinstructions for implementing the functionality specified in theflowchart block or blocks. The computer program instructions may also beloaded onto a computer or other programmable data processing apparatusto cause a series of operational steps to be performed on the computeror other programmable apparatus to produce a computer-implementedprocess such that the instructions that execute on the computer or otherprogrammable apparatus provide operations for implementing the functionsspecified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrationssupport various combinations for performing the specified functions,combinations of operations for performing the specified functions andprogram instructions for performing the specified functions. It shouldalso be understood that each block of the block diagrams and flowchartillustrations, and combinations of blocks in the block diagrams andflowchart illustrations, can be implemented by special purposehardware-based computer systems that perform the specified functions oroperations, or combinations of special purpose hardware and computerinstructions.

II. Exemplary System Architecture

FIG. 1 provides an illustration of a system that can be used inconjunction with various embodiments of the present invention. As shownin FIG. 1, the system may include one or more carrier systems 100, oneor more networks 105, one or more mobile devices 110, one or more usercomputing devices 115, and one or more kiosks 120. Each of thecomponents of the system may be in electronic communication with, forexample, one another over the same or different wireless or wirednetworks including, for example, a wired or wireless Personal AreaNetwork (“PAN”), Local Area Network (“LAN”), Metropolitan Area Network(“MAN”), Wide Area Network (“WAN”), or the like. Additionally, whileFIG. 1 illustrates certain system entities as separate, standaloneentities, the various embodiments are not limited to this particulararchitecture.

1. Exemplary Carrier System

FIG. 2 provides a schematic of a carrier system 100 according to oneembodiment of the present invention. In general, the term “system” mayrefer to, for example, any computer, computing device, mobile phone,desktop, notebook or laptop, distributed system, server, blade, gateway,switch, processing device, or combination of processing devices adaptedto perform the functions described herein. As will be understood fromthis figure, in one embodiment, the carrier system 100 includes aprocessor 205 that communicates with other elements within the carriersystem 100 via a system interface or bus 261. The processor 205 may beembodied in a number of different ways. For example, the processor 205may be embodied as a processing element, a coprocessor, a controller orvarious other processing devices including integrated circuits such as,for example, an application specific integrated circuit (“ASIC”), afield programmable gate array (“FPGA”), a hardware accelerator, or thelike.

In an exemplary embodiment, the processor 205 may be configured toexecute instructions stored in the device memory or otherwise accessibleto the processor 205. As such, whether configured by hardware orsoftware methods, or by a combination thereof, the processor 205 mayrepresent an entity capable of performing operations according toembodiments of the present invention when configured accordingly. Adisplay device/input device 264 for receiving and displaying data mayalso be included in the carrier system 100. This display device/inputdevice 264 may be, for example, a keyboard or pointing device that isused in combination with a monitor. The carrier system 100 furtherincludes memory 263, which may include both read only memory (“ROM”) 265and random access memory (“RAM”) 267. The carrier system's ROM 265 maybe used to store a basic input/output system (“BIOS”) 226 containing thebasic routines that help to transfer information to the differentelements within the carrier system 100.

In addition, in one embodiment, the carrier system 100 includes at leastone storage device 268, such as a hard disk drive, a CD drive, and/or anoptical disk drive for storing information on various computer-readablemedia. The storage device(s) 268 and its associated computer-readablemedia may provide nonvolatile storage. The computer-readable mediadescribed above could be replaced by any other type of computer-readablemedia, such as embedded or removable multimedia memory cards (“MMCs”),secure digital (“SD”) memory cards, Memory Sticks, electrically erasableprogrammable read-only memory (“EEPROM”), flash memory, hard disk, orthe like. Additionally, each of these storage devices 268 may beconnected to the system bus 261 by an appropriate interface.

Furthermore, a number of program modules may be stored by the variousstorage devices 268 and/or within RAM 267. Such program modules mayinclude an operating system 280, a billing module 270, a tracking module260, and an authorization module 250. These modules may control certainaspects of the operation of the carrier system 100 with the assistanceof the processor 205 and operating system 280—although theirfunctionality need not be modularized. In addition to the programmodules, the carrier system 100 may store or be connected to one or moredatabases (e.g., database 240) with one or more tables stored therein.

Also located within the carrier system 100, in one embodiment, is anetwork interface 274 for interfacing with various computing entities.This communication may be via the same or different wired or wirelessnetworks (or a combination of wired and wireless networks), as discussedabove. For instance, the communication may be executed using a wireddata transmission protocol, such as fiber distributed data interface(“FDDI”), digital subscriber line (“DSL”), Ethernet, asynchronoustransfer mode (“ATM”), frame relay, data over cable service interfacespecification (“DOCSIS”), or any other wired transmission protocol.Similarly, the carrier system 100 may be configured to communicate viawireless external communication networks using any of a variety ofprotocols, such as 802.11, general packet radio service (“GPRS”),wideband code division multiple access (“W-CDMA”), or any other wirelessprotocol. Via the network interface 274, the carrier system 100 may becapable of sending and receiving text messages and/or instant messages.

It will be appreciated that one or more of the carrier system's 100components may be located remotely from other carrier system 100components. Furthermore, one or more of the components may be combinedand additional components performing functions described herein may beincluded in the carrier system 100.

2. Exemplary Mobile Device

FIG. 3 provides an illustrative schematic representative of a mobiledevice 110 that can be used in conjunction with the embodiments of thepresent invention. As shown in FIG. 3, the mobile device 110 can includean antenna 312, a transmitter 304, a receiver 306, and a processingdevice 308 (e.g., a processor, controller, and/or the like) thatprovides signals to and receives signals from the transmitter 304 andreceiver 306, respectively.

The signals provided to and received from the transmitter 304 and thereceiver 306, respectively, may include signaling information inaccordance with an air interface standard of applicable wirelesssystems. In this regard, the mobile device 110 may be capable ofoperating with one or more air interface standards, communicationprotocols, modulation types, and access types. More particularly, themobile device 110 may operate in accordance with any of a number ofsecond-generation (“2G”) communication protocols, third-generation(“3G”) communication protocols, fourth-generation (“4G”) communicationprotocols, and/or the like. Further, for example, the mobile device 110may operate in accordance with any of a number of different wirelessnetworking techniques, including Bluetooth, IEEE 802.11 (“Wi-Fi”),802.16 (“WiMAX”), ultra wideband (“UWB”), and/or the like. Via thesecommunication standards and protocols, the mobile device 110 cancommunicate with the carrier system 100 and/or various other entities(e.g., user computing devices 110 or telephones 120). The mobile device110 can also download changes, add-ons, and updates, for instance, toits firmware, software (e.g., including modules), and operating system.

The mobile device 110 may also comprise a user interface (that caninclude a display 316 coupled to a processing device 308) and/or a userinput interface (coupled to the processing device 308). The user inputinterface can comprise any of a number of devices allowing the mobiledevice 110 to receive data, such as a keypad 318, a touch display, voiceor motion interfaces, or other input device. In embodiments including akeypad 318, the keypad 318 can include the conventional numeric (0-9)and related keys (#, *), and other keys used for operating the mobiledevice 110 and may include a full set of alphabetic keys or set of keysthat may be activated to provide a full set of alphanumeric keys. Inaddition to providing input, the user input interface can be used, forexample, to activate or deactivate certain functions, such as screensavers and/or sleep modes. Although not shown, the mobile device 110 mayalso include a battery, such as a vibrating battery pack, for poweringthe various circuits that are required to operate the mobile device 110,as well as optionally providing mechanical vibration as a detectableoutput.

The mobile device 110 can also include volatile memory 322 and/ornon-volatile memory 324, which can be embedded and/or may be removable.For example, the non-volatile memory may be embedded or removablemultimedia memory cards (“MMCs”), secure digital (“SD”) memory cards,Memory Sticks, EEPROM, flash memory, hard disk, or the like. The memorycan store any of a number of pieces or amount of information and dataused by the mobile device 110 to implement the functions of the mobiledevice 110. The memory can also store content, such as computer programcode for an application and/or other computer programs.

3. Exemplary Kiosk

As shown in FIG. 1, the system may include a kiosk 120. The kiosk 120may include one or more components that are functionally similar tothose of the carrier system 100. For example, a kiosk 120 may include:(1) a processor that communicates with elements via a system interfaceor bus; (2) a display device/input device; (3) memory including both ROMand RAM; (4) a storage device; (5) a network interface (including nearfield communication capabilities such as Bluetooth and capabilities forsending and receiving text messages and/or instant messages); (6)weighing mechanisms, such as scales; and/or (7) imaging devices. Thesearchitectures are provided for exemplary purposes only and are notlimiting to the various embodiments.

4. Additional Exemplary System Components

The user computing devices 115 may each include one or more componentsthat are functionally similar to those of the carrier system 100. Forexample, in one embodiment, each user computing device 115 may include:(1) a processor that communicates with other elements via a systeminterface or bus; (2) a display device/input device; (3) memoryincluding both ROM and RAM; (4) a storage device; and (5) a networkinterface. These architectures are provided for exemplary purposes onlyand are not limiting to the various embodiments. The term “computingdevice” is used generically to refer to any computer, mobile phone,computing device, desktop, notebook or laptop, distributed system,server, gateway, switch, or other processing device adapted to performthe functions described herein.

III. Exemplary System Operation

Reference will now be made to FIGS. 4-7. FIGS. 4-5 provide flowchartsillustrating operations that may be performed for shipping parcels. FIG.6 is an exemplary drop-box 600 at which parcels can be dropped off for acarrier (e.g., United Parcel Service of America, Inc.). And FIG. 7 showsexemplary input/output that can be produced via a mobile device 110.

1. Message-Based Shipments

In one embodiment, customers/users can use electronic messages toinitiate shipment of and payment for shipping a parcel.

a. Initiation of Shipment

In one embodiment, a customer/user can use, for example, a drop-box 600(such as the one shown in FIG. 6) to initiate shipment of a parcel(e.g., envelope, bag, package, bundled item, box with informationpre-printed thereon, and/or the like) by a carrier (e.g., United ParcelService of America, Inc.). For instance, the user can retrieve ashipping form (or a box or envelope with information pre-printedthereon) that may be stored proximate the drop-box 600 (or othershipping location) and fill out the shipping form (or box or envelopewith information pre-printed thereon) with shipping information. Theshipping information may include information such as (a) the consignor'sname, address, phone number, and charge card number (or a portionthereof), (b) the contents, weight, and dimensions of the parcel, (c)the consignee's name, address, and phone number, (d) the class ofservice of the parcel (e.g., Ground, Next Day Air, etc.), and/or (e) avariety of other information. The shipping form (or box or envelope withinformation pre-printed thereon) may also include a unique, pre-printedtracking number. The tracking number may be, for example, a progressivenumber (“PRO number”), a purchase order number, and/or a set ofalphanumeric characters (e.g., “1Z23456789”). The tracking number may beused by the carrier to identify and track the parcel as it travelsthrough the carrier's transportation and logistics network. To that end,the shipping form may have a self-adhesive portion, for example, thatcan be used to adhere the shipping form to the parcel or adhere a labelportion of the shipping form to the parcel.

As shown in FIG. 4, in one embodiment, after (or in some cases before)filing out the shipping form (or box or envelope with informationpre-printed thereon), the customer/user can initiate shipment of theparcel with carrier. To do so, the customer/user may send a message(e.g., a first message) via a user device (e.g., a mobile device 110 ora user computing device 115) to the carrier. For example, the shippingform, drop-box 600, box, or envelope may indicate that to initiateshipment of a parcel, a text message should be sent to 555-555-5555 withthe tracking number printed on the shipping form as the body of themessage. Thus, in one embodiment, the customer/user (e.g., via operationof user device such as a mobile device 110 or user computing device 115)sends a text message to 555-555-5555 with 1Z23456789 as the body of themessage. As will be recognized, though, the message may be any type ofmessage, such as a text message, an instant message, an email message,and/or the like. Similarly, the message may include a variety ofshipping information, such as the pre-printed tracking number listed onthe shipping form, a charge card number (or a portion thereof), and/or acarrier account number (or a portion thereof).

As indicated in Block 400, in one embodiment, a carrier entity (e.g., acarrier system 100) can receive the first message (e.g., text message)sent from the user device (e.g., mobile device 110 or user computingdevice 115) requesting shipment of the parcel. In response to receivingthe first message, the carrier system 100, for example, can identify anaccount identifier based at least in part on the first message. In oneembodiment, the account identifier may correspond to an accountassociated with the customer/user (Block 405). The account identifiermay be, for example, a phone number of the mobile device 110 from whichthe first message originates, the phone number associated with anapplication executing on a user computing device 115 from which thefirst message originates, a credit card number (or a portion thereof)within the body of the first message, and/or a carrier account number(or a portion thereof) within the body of the first message.Accordingly, the account corresponding to the account identifier may be(a) an account for wireless services (e.g., phone and/or data services),(b) an account for a charge card, (c) a shipping account with thecarrier, and/or (d) a variety of other accounts.

As shown in Block 410, after identifying the account identifier, thecarrier system 100 can determine whether the account is valid.Determining whether the account is valid may include a variety oftechniques and/or approaches. For example, in one embodiment, thecarrier system 100 determines whether the account associated with thephone number is valid by electronically communicating with the wirelessservices provider to determine whether the account is active, in goodstanding, and/or available for mobile payments. For instance, a phonenumber in a family plan may be blocked for mobile payments via parentalcontrols provided by the wireless services provider. Similarly, thewireless services provider may block messages to certain prefixes, suchas 900 numbers. In another embodiment, the carrier system 100 maydetermine whether the carrier has “blacklisted” the phone number, forexample, corresponding to the account. In another embodiment, thecarrier system 100 may determine whether the account corresponding tothe charge card number is valid by determining whether the charge cardaccount is active and in good standing.

In addition to the determining whether the account is valid, the carriersystem 100 (e.g., via the authorization module 250) can execute variousother validation/confirmation techniques and/or approaches. For example,the carrier system 100 can determine whether the tracking number in thebody of the first message has been used previously. Or, the carriersystem 100 can access (a) the transaction history of thecustomer's/user's interactions with the carrier and/or (b) anycustomer/user configured parameters. For example, a customer/user canregister mobile phone numbers with carrier (e.g., via the carrier'swebsite) to configure usage parameters. The usage parameters may, forexample, (a) limit a phone number to one shipment per day, (b) not allowfor international shipments using the phone number, and/or (c) limit themobile payments for shipping to $100 per day. As will be recognized, avariety of approaches and/or techniques may be used.

In one embodiment, as indicated in Block 415, in response to adetermination that the account is invalid, the carrier system 100 (e.g.,via the authorization module 250) can generate and transmit a message(e.g., a second message) to the user device (e.g., mobile device 110 oruser computing device 115). As with the first message, the secondmessage may be any type of message, such as a text message, an instantmessage, an email message, and/or the like. In an embodiment in whichthe account is invalid, the second message may indicate that thecustomer/user cannot use the selected method of payment for shipping theparcel.

In one embodiment, as indicated in Block 420, in response to adetermination that the account is valid, the carrier system 100 cangenerate and transmit a message (e.g., a second message) to the userdevice (e.g., mobile device 110 or user computing device 115). Asindicated, the second message may be any type of message, such as a textmessage, an instant message, an email message, and/or the like. In anembodiment in which the account is valid, the second message maycomprise an authorization code for shipment of the parcel. Theauthorization code may be, for example, an alphanumeric code (e.g.,“A254”) that has been correlated with the tracking number and/or theshipping information provided by the customer/user.

In one embodiment, the authorization code may also be associated withvarious predefined parameters. For example, the authorization code maybe associated with predefined parameters that define (a) a time periodin which the authorization code is valid and/or (b) the number of timesthe authorization code can be used for shipments. For instance, theauthorization code may only be valid for a single shipment. Similarly,the authorization code may be valid for a certain period of time (e.g.,7 days) after issuance. As will be recognized, a variety of otherapproaches and techniques may be used.

In one embodiment, after the user device (e.g., mobile device 110 oruser computing device 115) receives the second message, the user device(e.g., mobile device 110 or user computing device 115) can cause displayof the second message to the customer/user, as shown in FIG. 7. Thecustomer/user can write the authorization code on the parcel, label, orshipping form, for example. The customer/user can then deliver theparcel to a drop-box 600 or other carrier location/facility.Alternatively, the customer/user may request that a carrier vehicle bedispatched to pick up the parcel from the customer/user. Upon receipt ofthe parcel, the carrier can use the shipping information and/orauthorization code in transporting the parcel through the carrier'stransportation and logistics network.

b. Shipment

In one embodiment, after the carrier receives the parcel from thecustomer/user (consignee), the carrier can begin transport of the parcelthrough the carrier's transportation and logistics network. Parcelsmoving through the carrier's transportation and logistics network aretypically tracked by scanning a label (e.g., barcode, radio frequencyidentification (“RFID”) tag, etc.), shipping form, or other indiciaassociated with the parcel at one or more scan points. For example, at atransportation hub, one or more scanning devices may be used to scan alabel associated with the parcel (or box or envelope) to captureshipping information from the parcel. Additionally or alternatively, animage of the label on the parcel, for instance, may be captured by oneor more imaging devices. As with scanning the parcel, the image of thelabel on the parcel may comprise shipping information (such as thetracking identifier and/or the authorization code) that may be humanreadable and/or machine readable.

In one embodiment, the image of the parcel can then be transmitted toand received by the carrier system 100 (Block 425). The carrier system100 can then receive/identify shipping information contained in theimage. The carrier system 100 (e.g., via the tracking module 260) canreceive/identify the shipping information using a variety of techniquesand approaches. For example, a user (e.g., a carrier employee) can readthe shipping information from the image and input the same via aninterface into the carrier system 100. In another embodiment, an opticalcharacter recognition (“OCR”) feature can be used to extract theshipping information from the image. As will be recognized, a variety ofother techniques and approaches can be used.

As a result of receiving/identifying the shipping information as theparcel is transported within a carrier's transportation and logisticsnetwork, the carrier system 100 can determine whether the parcel isapproved for shipment (Block 430). In determining whether the parcel isapproved for shipment, the carrier system 100 can, for example,determine whether the authorization code used to ship the parcel isvalid. The carrier system 100 may also determine whether theauthorization code and/or parcel are in compliance with any predefinedparameters associated with the authorization code (e.g., time period orusage parameters). Determining whether the parcel is approved forshipment may also include determining whether the account is stillvalid. As discussed above, this may include electronically communicatingwith the wireless services provider or charge card company to determinewhether (a) the account associated with the phone number is stillactive, in good standing, and/or available for mobile payments and/or(b) the account corresponding to the charge card is still active and ingood standing. Similarly, this may include determining, for example,whether the carrier has blacklisted the phone number corresponding tothe account.

In one embodiment, in response to a determination that the parcel isapproved for shipment, the carrier system 100 can store the shipmentinformation in association with the tracking identifier, theauthorization code, and/or the account identifier (Block 435). In oneembodiment, this may include automatically creating a parcel leveldetail (“PLD”) record. The PLD record may include shipping information,such as the consignor's address, the consignor's mobile phone number,the authorization code, the tracking number, the consignee's address,the class of service, and/or the method of payment. As will berecognized, the storage of this information may occur at any pointduring the process, such as after receiving the first messagetransmitted from the user device.

In one embodiment, if the parcel is approved for shipment, the parcelcontinues to be transported through the carrier's transportation andlogistics network to the consignee and/or destination address. If theparcel is not approved for shipment (e.g., the account associated withwireless phone number is not active and/or in good standing), the parcelcan be held by the carrier or returned to the consignor. For example, aflag (e.g., an exception event) may be stored in the PLD recordindicating that shipment of the parcel should be held or returned to theconsignor. In the event the parcel is held by the carrier, carrierrepresentative's can contact the consignor to receive an alternativemeans of payment for shipment of the parcel.

c. Payment for Shipment

In one embodiment, as the parcel is transported through the carrier'stransportation and logistics network to the consignee and/or destinationaddress, the shipping charges for shipment of the parcel may beautomatically determined. For example, the parcel may pass throughautomatic scanners, imaging devices, scales, and/or the like within thecarrier's transportation and logistics network. Thus, for instance, asthe parcel passes over a scale, the weight of the parcel canautomatically be determined. Additionally, imaging devices, such asdigital cameras, can capture images of the parcel. The carrier system100 can use the images of the parcel to, for example, determine thedimensions of the parcel. With the weight, dimensions, and class ofservice of the parcel, the carrier system 100 (e.g., via the billingmodule 270) can determine the appropriate shipping charges for shipmentof the parcel (Block 440).

In one embodiment, after determining the shipping charges for theparcel, the carrier system 100 (e.g., via the billing module 270) cancharge the appropriate account for shipment of the parcel (Block 445).As discussed above, the account may be (a) an account for wirelessservices (e.g., phone and/or data services), (b) an account for a chargecard, (c) a shipping account with the carrier, and/or (d) a variety ofother accounts. In one embodiment, the carrier system 100 (e.g., via thebilling module 270) can charge (e.g., process) the shipping charges toaccounts in batch, such as batch processing the transaction hourly ornightly. In another embodiment, the carrier system 100 (e.g., via thebilling module 270) can charge the appropriate accounts in real time ornear real time. Thus, after the carrier system 100 charges theappropriate account, the customer/user can be billed, for example, byhis wireless services provider for the shipping charges at the end ofhis billing cycle. The wireless services provider can also settle thecharges with the carrier.

In one embodiment, in addition to charging the appropriate account, thecarrier system 100 may provide additional information (e.g., thetracking number and/or the authorization code) to the appropriate entity(e.g., wireless service provider, charge card company, etc.) whencharging the account. This information may be included, for example, onthe customer's/user's bill. For instance, the wireless services providercan use this additional information to provide the details of theshipment on the customer's/user's bill for wireless services.

d. Additional Concepts

As will be recognized, a variety of other approaches and techniques maybe used. For example, in one embodiment, the carrier system 100 canstore a charge card number in association with a phone number for thecustomer/user. Thus, the customer/user can provide a phone number as theaccount identifier in the first message, but the charge card accountcould be charged for the shipment of the parcel—instead of the accountwith the wireless services provider. Similarly, the carrier system 100can store a carrier account number in association with a phone number.This may allow the customer/user to provide a phone number as theaccount identifier in the first message, but the carrier account couldbe charged for the shipment of the parcel—instead of the account withthe wireless services provider.

2. Kiosk-Based Shipments

In one embodiment, a customer/user can use an apparatus, such as a kiosk120, to initiate shipment of and payment for shipping a parcel.

a. Initiation of Shipment and Shipment

In one embodiment, a customer/user can use a kiosk 120, for example, toinitiate shipment of a parcel (e.g., envelope, bag, package, bundleditem, box with information pre-printed thereon, and/or the like) by acarrier. As indicated, the kiosk 120 may have key entry and displayfeatures that allow customers/users to interact with the kiosk 120. Inone embodiment, the process beings with the kiosk 120 receiving inputrequesting shipment of a parcel, e.g., via a customer/user inputtinginformation into the kiosk 120 (Block 500). In response to receivingthis input, the kiosk 120 can cause display of a request for input ofshipping information and/or a method of payment for shipping the parcel(Block 505). As discussed previously, the shipping information mayinclude information such as (a) the consignor's name, address, phonenumber, and charge card number (or a portion thereof), (b) the contents,weight, and dimensions of the parcel, (c) the consignee's name, address,and phone number, (d) the class of service of the parcel (e.g., Ground,Next Day Air, etc.), and/or (e) a variety of other information. Thepayment options may include paying for the shipment via (a) a chargecard, (b) an account for wireless services, (c) an account with thecarrier, (d) a physical form of currency, and/or (e) the like. In oneembodiment, in response to causing display of the request for the methodof payment for shipment of the parcel, the kiosk 120 may receive input(a) indicating that the customer/user desires to pay for the shipmentvia an account for wireless services (Block 510) and (b) identifying aparticular phone number associated with the account for wirelessservices.

In one embodiment, in response to receiving input indicating that thecustomer/user desires to pay for shipment via the account for wirelessservices and the corresponding phone number, the carrier system 100 candetermine whether the account for wireless services is valid (Block515). As discussed above, determining whether the account is valid mayinclude a variety of techniques and/or approaches. For example, in oneembodiment, the carrier system 100 determines whether the accountassociated with the phone number is valid by electronicallycommunicating with the wireless services provider to determine whetherthe account is active, in good standing, and/or available for mobilepayments. For instance, a phone number in a family plan may be blockedfor mobile payments via parental controls provided by the wirelessservices provider. Similarly, the wireless services provider may blockmessages to certain prefixes, such as 900 numbers. In anotherembodiment, the carrier system 100 may determine whether the carrier hasblacklisted the phone number, for example, corresponding to the account.In another embodiment, the carrier system 100 may determine whether theaccount corresponding to the charge card number is valid by determiningwhether the charge card account is active and in good standing.

In one embodiment, as indicated in Block 520, in response to adetermination that the account is invalid, the kiosk 120/carrier system100 (e.g., via the authorization module 250) can generate and transmit amessage to the user device (e.g., mobile device 110 or user computingdevice 115). As discussed above, the message may be any type of messageand indicate that the customer/user cannot use the selected method ofpayment for shipping the parcel.

In one embodiment, as indicated in Block 525, in response to adetermination that the account is valid, the kiosk 120/carrier system100 (e.g., via the authorization module 250) can generate and transmit amessage comprising an authorization code to the user device. Asdiscussed above, the message may be any type of message and include anauthorization code. The authorization code may be, for example, analphanumeric code (e.g., “A254”) that has been correlated with thetracking number and/or the shipping information. The authorization codemay also be associated with various predefined parameters. For example,the authorization code may be associated with predefined parameters thatdefine (a) a time period in which the authorization code is valid and/or(b) the number of times the authorization code can be used forshipments. For instance, the authorization code may be valid for asingle shipment or multiple shipments. Similarly, the authorization codemay be valid for a certain period of time (e.g., 7 days) after issuance.As will be recognized, a variety of other approaches and techniques maybe used.

In one embodiment, in addition to generating and transmitting a messageto the user device (or an account, such as Gmail, Skype, etc.), thekiosk 120 can cause display of a request for input of the authorizationcode transmitted to the user device (Block 530). Thus, after thecustomer's/user's user device (e.g., mobile device 110) receives themessage with the authorization code (e.g., see FIG. 7), thecustomer/user can input the authorization code into the kiosk 120 (Block535).

In one embodiment, in response to receiving input of the correctauthorization code, the kiosk 120 can cause display of additionalrequests for input, for example, to properly classify the parcel. Forinstance, the kiosk 120 can cause display of text instructing thecustomer/user to place the parcel on a scale proximate (or disposed on)the kiosk 120. By doing so, the kiosk 120 can determine the actualweight of the parcel. The kiosk 120 can also cause display of textinstructing the customer/user to input (e.g., via key entry) thedimensions of the parcel. For example, the customer/user may input thedimension of the parcel in appropriate length, width, and height fields.As will be recognized, a variety of approaches and techniques may beused.

In one embodiment, after receiving the appropriate input (e.g., weight,dimensions, and class of service of the parcel), the kiosk 120 (orcarrier system 100) can determine the appropriate shipping charges forshipment of the parcel (Block 540). For example, if a customer/userenters the dimensions of the parcel as 10×10×10 (e.g., length, width,and height) and the kiosk 120 determines the parcel weighs 2 pounds, thekiosk 120 may provide a notification to the customer/user that theparcel is classified as being a high volume, low weight parcel and causedisplay of the corresponding shipping charge. Additionally, the kiosk120 may add a surcharge for certain destinations (e.g., rural areas) orcontents (e.g., hazardous materials) of the parcel. As will berecognized, a variety of approaches and techniques may be used.

In addition to determining the shipping charges, the kiosk 120 (orcarrier system 100) may store the shipping information associated withthe parcel and/or the customer/user (Block 545). For example, the kiosk120/carrier system 100 may create a PLD record to store the shippinginformation, such as the consignor's address, the consignor's mobilephone number, the authorization code, the consignee's address, trackingnumber, class of service, and/or method of payment.

In one embodiment, in addition to storing the shipping information, thekiosk 120 may automatically print a shipping label to be affixed to theparcel (Block 545). After the kiosk 120 prints the shipping label, thecustomer/user can adhere the shipping label to the parcel. Thecustomer/user can then deliver the parcel to the kiosk 120, a drop-box600, or other carrier location/facility. Upon receipt of the parcel, thecarrier can transport the parcel through the carrier's transportationand logistics network to the consignee and/or destination address.

b. Payment for Shipment

In one embodiment, the kiosk 120/carrier system 100 (e.g., via thebilling module 270) can charge the appropriate account for shipment ofthe parcel (Block 550). As discussed above, the account may be anaccount for wireless services (e.g., phone and/or data services) and/ora variety of other accounts as described above. Thus, the customer/usercan be billed by his wireless services provider for the shipping chargesat the end of his billing cycle. Correspondingly, the wireless servicesprovider can then settle the shipping charges with the carrier.

In one embodiment, in addition to charging the appropriate account, thecarrier system 100 may provide additional information (e.g., thetracking number and/or the authorization code) to the appropriate entity(e.g., wireless service provider, charge card company, etc.) whencharging the account. This information may be included, for example, onthe customer's/user's bill. For instance, the wireless services providercan use this additional information to provide the details of theshipment on the customer's/user's bill for wireless services.

c. Additional Concepts

As will be recognized, a variety of other approaches and techniques maybe used. For example, in one embodiment, in response to a determinationthat the account is valid, the kiosk 120 may automatically initiatecommunication with a mobile device 110 associated with the account forwireless services. Thus, in lieu of sending a message with anauthorization code to the user device (e.g., mobile device 110), thekiosk 120 can communicate via a communication standard/protocol (e.g.,Bluetooth) to confirm that the customer/user is currently in possessionof the user device.

IV. Conclusion

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing descriptions and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation.

1. A method for shipping a parcel, the method comprising: receiving, viaone or more processors, input from a user requesting shipment of aparcel; causing display of a request for input identifying a method ofpayment for shipment of the parcel; in response to causing display ofthe request for input of the method of payment for shipment of theparcel, receiving input (a) identifying an account for wireless servicesas the method of payment and (b) a phone number associated with theaccount for wireless services; determining whether the account forwireless services is valid; in response to a determination that theaccount for wireless services is valid, generating and transmitting amessage to a mobile device associated with the phone number, wherein themessage comprises an authorization code; causing display of a requestfor input of the authorization code transmitted to the mobile device;and receiving input from the user identifying the authorization code. 2.The method of claim 1 further comprising: in response to receiving inputidentifying the authorization code, automatically (a) printing ashipping label to be affixed to the parcel and (b) storing theauthorization code in association with the phone number, a trackingnumber, and shipment information; electronically determining shippingcharges for shipment of the parcel; and electronically charging theshipping charges to the account.
 3. The method of claim 2, whereinelectronically determining the shipping charges for shipment of theparcel further comprises automatically determining a weight of theparcel.
 4. The method of claim 1, wherein the authorization code isassociated with predefined parameters.
 5. The method of claim 4, whereinthe predefined parameters define (a) a time period in which theauthorization code is valid and (b) the number of times theauthorization code can be used for shipments.
 6. The method of claim 1,wherein the message is selected from the group consisting of a textmessage and an instant message.
 7. A method for shipping a parcel, themethod comprising: receiving, via one or more processors, input from auser requesting shipment of a parcel; causing display of a request forinput identifying a method of payment for shipment of the parcel; inresponse causing display of the request for input of the method ofpayment for shipment of the parcel, receiving input identifying anaccount for wireless services as the method of payment; in response toreceiving input identifying the account for wireless services as themethod of payment, automatically initiating communication with a mobiledevice associated with the account for wireless services; anddetermining whether the account for wireless services is valid.
 8. Themethod of claim 7 further comprising: in response to a determinationthat the account for wireless services is valid, automatically (a)printing a shipping label to be affixed to the parcel and (b) storingthe authorization code in association with the phone number, a trackingnumber, and shipment information; electronically determining shippingcharges for shipment of the parcel; and electronically charging theshipping charges to the account.
 9. The method of claim 8, whereinelectronically determining the shipping charges for shipment of theparcel further comprises automatically determining a weight of theparcel.
 10. The method of claim 7, wherein the authorization code isassociated with predefined parameters.
 11. The method of claim 10,wherein the predefined parameters define (a) a time period in which theauthorization code is valid and (b) the number of times theauthorization code can be used for shipments.
 12. The method of claim 7,wherein the message is selected from the group consisting of a textmessage and an instant message.
 13. A computer program product forshipping a parcel, the computer program product comprising at least onecomputer-readable storage medium having computer-readable program codeportions stored therein, the computer-readable program code portionscomprising: an executable portion configured to receive input from auser requesting shipment of a parcel; an executable portion configuredto cause display of a request for input identifying a method of paymentfor shipment of the parcel; an executable portion configured to, inresponse to causing display of the request for input of the method ofpayment for shipment of the parcel, receive input identifying (a) anaccount for wireless services as the method of payment and (b) a phonenumber associated with the account for wireless services; an executableportion configured to determine whether the account for wirelessservices is valid; an executable portion configured to, in response to adetermination that the account for wireless services is valid, generateand transmit a message to a mobile device associated with the phonenumber, wherein the message comprises an authorization code; anexecutable portion configured to cause display of a request for input ofthe authorization code transmitted to the mobile device; and anexecutable portion configured to receive input from the user identifyingthe authorization code.
 14. The computer program product of claim 13further comprising: an executable portion configured to, in response toreceiving input identifying the authorization code, automatically (a)print a shipping label to be affixed to the parcel and (b) store theauthorization code in association with the phone number, a trackingnumber, and shipment information; an executable portion configured todetermine shipping charges for shipment of the parcel; and an executableportion configured to determine charge the shipping charges to theaccount.
 15. The computer program product of claim 14, wherein theexecutable portion configured to determine the shipping charges forshipment of the parcel is further configured to automatically determinea weight of the parcel.
 16. The computer program product of claim 13,wherein the authorization code is associated with predefined parameters.17. The computer program product of claim 16, wherein the predefinedparameters define (a) a time period in which the authorization code isvalid and (b) the number of times the authorization code can be used forshipments.
 18. The computer program product of claim 13, wherein themessage is selected from the group consisting of a text message and aninstant message.
 19. A computer program product for shipping a parcel,the computer program product comprising at least one computer-readablestorage medium having computer-readable program code portions storedtherein, the computer-readable program code portions comprising: anexecutable portion configured to receive input from a user requestingshipment of a parcel; an executable portion configured to cause displayof a request for input identifying a method of payment for shipment ofthe parcel; an executable portion configured to, in response causingdisplay of the request for input of the method of payment for shipmentof the parcel, receive input identifying an account for wirelessservices as the method of payment; an executable portion configured to,in response to receiving input identifying the account for wirelessservices as the method of payment, automatically initiate communicationwith a mobile device associated with the account for wireless services;and an executable portion configured to determine whether the accountfor wireless services is valid.
 20. The computer program product ofclaim 19 further comprising: an executable portion configured to, inresponse to a determination that the account for wireless services isvalid, automatically (a) print a shipping label to be affixed to theparcel and (b) store the authorization code in association with thephone number, a tracking number, and shipment information; an executableportion configured to determine shipping charges for shipment of theparcel; and an executable portion configured to charge the shippingcharges to the account.
 21. The computer program product of claim 20,wherein electronically determining the shipping charges for shipment ofthe parcel further comprises automatically determining a weight of theparcel.
 22. The computer program product of claim 19, wherein theauthorization code is associated with predefined parameters.
 23. Thecomputer program product of claim 22, wherein the predefined parametersdefine (a) a time period in which the authorization code is valid and(b) the number of times the authorization code can be used forshipments.
 24. The computer program product of claim 19, wherein themessage is selected from the group consisting of a text message and aninstant message.